I think this myth has been thoroughly busted (see Bullet Therapist Posted: 2015.01.09 22:27 in this thread as an example) and is just used to misdirect the conversation. Indefinite cloaking is about being AFK and not having any risk to be holed up in the system.

Also, trying to tie indefinite cloaking to local chat is apples and oranges. Whether local should be changed or not, doesn't negate the immunity the cloaker has to sit indefinitely without threat in a hostile environment. Yes, both provide intel, but if you really wanted intel you could cycle your alliance members through the system each taking turns cloaking (or your alts) to offset whatever mechanic is put in place to limit indefinite cloaking.

Redundant thread is redundant?
Cloak have some disadvantages i would rather have a discuss about d-scan mechanics, sometimes i feel like playing "Push d-scan button online".

Operating on the principle that Local Is The ProblemGäó, I thought I'd brainstorm some Dscan ideas.

Local in Null currently provides the following information:
1. Number of pilots in system.
2. Name, Corp, etc, of all pilots in system.

#1 is essential to pvp and pve in all forms. If you don't know whether there are targets in system or not, you can't roam for targets. So this is something we need to keep. #2 IMO goes too far, and makes identifying those targets trivially easy. However, identifying targets DOES need to be done, but it should take some effort. Keep in mind this goes both ways, for pvp and pvp avoidance; that's how the cat and mouse game works. It wouldn't be a game worth playing otherwise.

So on these principles, I suggest that a dscan overhaul include the following features:
1. A "ping" that identifies the number of active pilots in system. (Lore: Ships with an active warp core have an easily identifiable scan signature. Shut down or unoccupied ships do not.) Does not function in wormholes due to "interference" (yay technobabble)
2. Range dependent intel gathering.
-At long range it only reports number of ships in radius, and number of those ships that are active.
-At medium range it also reports the name and type of ship. (this is the current level of Dscan info)
-At close range it also reports the Corp/Ticker.
-Identifying pilots by name is not possible until you see them on grid.
3. Alter range with the angle function.
-A 5 degree scan may have a max range of 64 AU; a 360 degree scan will be limited to more like 20 AU. "Medium Range" represents the current function of Dscan, so we can set that at the current 14 AU.
-This allows active scouts to quickly recon a system; it makes dscan/recon a valuable RL skill, similar to probing; it makes scouting a more important fleet role and gameplay function. It gives a hunter an intel advantage vs prey, but still allows prey a margin of defense.
4. Cloaking: While on grid with a cloaker, allow Dscan to provide a vector to the cloaked target. This make hunting cloakers possible, but preserves the "safe while in deep space" function.

Lastly, integrate these new features into the UI somehow. Either on the new map or on the sensor overlay. Lists in windows are important, but they are very "Spreadsheets in Space"-ey. Showing the Dscan cone in space, or in the map window would be awesome. Actually, this feature currently exists in a limited form on the f11 map, but the f11 map sucks, so yeah. Improve on that.

When responding to this post, remember this is just a brainstorm.

When all this, or something like it, is done, the cloak/afk problem will be mitigated. The hunter/prey gameplay will be redone and null will much more exciting. Then we can move Nullsec Local to the Delayed system.

Can you activate a cyno while cloaked? Or activate anything while cloaked, for that matter?

If you've got cloaky eyes in a system, and you've use him before, there's a good chance I know if you're going to use him or not. If I've seen a cloaker make a move one time, I've watch listed, cataloged, and made notes on every other person on the killmail they produce, if any. By correlating this information with killboard histories, I (or potentially any player) am able to discern, with a resonable chance of success, whether that character is active or not. It's hard to have a psychological effect if the people your trying to affect know that you're impotentently sitting afk.

I think you have less of a grasp on the game mechanics than you claim. Dealing with afk cloakers and establishing system security, for those whom are interested, is a mixture of activities that requires correlating details into a bigger picture with the intent of understanding the risk posed by a situation. Cloakers are less threatening than most of the people here believe because we have the tools to understand when they're going to be active or not when they've been used. The problem is intel, more specifically, the quality of the intel relative to the risk that cloakers place themselves in.